Things To Do
------------

 1. Make modifications to the RFM to allow large files to be sliced up into
    small parts for transmission over a period of time.  Also add commands to
    allow the initiator to specify the user(s) who should be notified of the
    status of the transfer.  Add a command to set the verbose level of the
    status messages (how often the status messages are sent out).
 2. Finish the NNS (Network Name Server).
 3. Allow remote new user requests.
 4. Allow access flags on entire areas in xfers or msg base.
 5. Allow users to lock out entire areas from scanning in the msg base.
 6. Allow users to grant others access to their home directory.
 7. Add user configuration flag to disable the showing of the auto login msg.
10. Enhance groups.  Allow ability for people to add themselves to a group if
    they so desire.  Make adding to groups easier.
12. Write posts leave moustext on or something.
13. For bundles, auto-unbundle into a DIRECTORY called "UPD.xxx"!
14. Aborting "answer" in message base still bumps post counter.
15. Return stack gets fucked in (T)emplate editor in M1.  Also can't enter "Q"
    when prompted for template numbers [editing a user, etc]
18. Threading:

Here's another suggestion to file in the "To Improve" folder for someday when
you have a few free mintues....

The threading option is a LITTLE slower than it needs to be because no matter
WHAT message it accesses, it prints the text control "Ctrl-S to Slow...."
header. This is REALLY a waste...how about having it disply a running counter
like the Find message option does? It'd save some time at lower baud rates
and the actual code would go faster.

Just a suggestion, cause the threading option IS real slow! It works, but it's
a dog! And when you are dealing with 1024 messages in one message base, it
tends to drag a bit.

ALSO..once the last message in a thread has been reached, the message pointer
should be returned BACK to the original message in the thread. This way, a
user can start with a message and read all the pertinent shit, then go back
and read the next messages.

19. Allow messages to be tagged as "undeletable".  For autokill, we'd have
    to check to see if the message is tagged; if it is, try deleting the one
    after it instead.

20. Allow users to set up one or more "form letters" that could be used as
    a way to quick-reply to letters.  This would be great for letting me
    send back a "thank you for your bug report" letter to everyone!

21. Distribution list ability for network conference posts.  This also
    implies that the net site lists would have to contain more detailed
    information (ie, location information for the site)

    This can be done in part by adding a new optional line to the message
    headers, entitled "Distribution:", and it could have values like
    "WORLD","USA","MICHIGAN","OHIO", etc.

22. Ability to mark posts as "private replies only"

23. Switchable hotkeys.  When off, you could seperate commands with
    semicolons and they'd be executed in sequence (ala TradeWars)

25. Show connect time for net dialouts in the net log.

26. Ability to add comments to letters being manually forwarded

27. Automatic archiving of message bases.  When autokill is on, as the
    autokill msg is deleted it is appened to a text file for archiving.

28. Ability to mark AND unmark mail for deletion.

29. Ability to enable/disable hashing

30. Make dump mode affect only the current subboard

31. Let users use "<" and ">" to go back/forward in quickscan

32. Ability to set hour-by-hour universal time limits, so that users calling
    during peak hours could be restricted to less time online.
